% subsection of Project Overview Statement

\section{Success Criteria}\label{sec:successcriteria}

This section describes how the authors have planned to validate the projects
outcome to make sure to meet the clients needs. This corresponds to the clients
acceptance criteria.

For each of the given criteria a brief explanation in prose is given followed
up by a short summary catagorised in pre and post-condition.

\subsection{Infrastructure Related Criteria}

\subsubsection{Performance and Configuration of Data Turbine}
	There is comprehensive documentation available to install and configure Data
	Turbine either in form of a script or step-by-step instruction in such a way,
	that it is operational. Instructions are also provided to measure performance
	of Data Turbine and monitor processed data.
	
	\begin{description}
		\item[Pre-Condition] A standard linux distribution installed on a x86 32-Bit
		hardware.
		\item[Post-Condition] A operational Data Turbine installation.
    \end{description}

\subsection{Producer Glue Related Criteria}

\subsubsection{Communication with SAL via RMI}
	There is a software implementation available, which is able to connect to a
	remote running SAL server agent. 
	
	\begin{description}
			\item[Pre-Condition] A operational SAL server agent accessible via RMI.
			\item[Post-Condition] SAL-T displays connected sensors to the remote
			SAL server agent.
	\end{description}		

\subsubsection{Sensor data is read and sent to Data Turbine (DT)}
	 There is a software implementation available which is able to connect to a
	 running SAL server agent. For each sensor connected to the SAL server agent
	 the software implementation polls in configurable intervals for the data
	 provided by the sensor. The interval is configurable individually for each
	 sensor type in milliseconds before execution time. The supported sensor types
	 are listed below:
 
	 \begin{itemize}
	  \item video
	  \item 1-wire
	  \item snmp
	  \item os data 
     \end{itemize}
     
     The fetched data is send to the DT, which can be visualised by
     a monitoring tool attached to DT.
         
	\begin{description}
			\item[Pre-Condition] A operational DT installation and an
			operational SAL server agent.
			\item[Post-Condition] Data for each connected/specified sensor is
			send to DT in defined intervals.
	\end{description}

\subsection{Sensor data is enriched with metadata when sent to Data Turbine}
	There is a software implementation available which is able to correlate data
	fetched from sensors with metadata. This metadata consists of the listed
	below.
	
	\begin{itemize}
	  \item sensor identifier
	  \item timestamp
     \end{itemize}
	
	\begin{description}
			\item[Pre-Condition] A operational DT installation and an
			operational SAL server agent.
			\item[Post-Condition] Data for each connected/specified sensor is
			sent to DT with sensor identifier and timestamp.
	\end{description}

\subsubsection{Communication with SAL via local objects/direct communication}
	\textit{This is an optional success criteria.}

	There is a software implementation available, which is able to be connected to
	a local running SAL server agent. The connection is realised in such a way that
	the software implementation is getting part of SAL. This implies there is only
	one java class needed to startup SAL together with SAL-T.
	
	\begin{description}
			\item[Pre-Condition] A operational SAL server agent.
			\item[Post-Condition] SAL-T displays connected sensors and their data
			when started with SAL.
	\end{description}

\subsection{Consumer Glue Related Criteria} 

\subsubsection{Format of sensor data to be stored in SRB is
specified}\label{sec:req_dataformat} There is a documentation available describing the format to be used
	for storing sensor data within a SRB.	

\subsubsection{Sensor data is dumped into a SRB}
	There is a software implementation available which is able to receive sensor
	data from the Data Turbine and store it within a SRB using the determined
	format of \autoref{sec:req_dataformat}. To abstract from the SRB in order to
	provide a higher degree of flexibility Commons VFS with GRID enhancements is
	used. The incoming data can be visualised with already available SRB browser
	(see \cite{hermes}).
	
	\begin{description}
			\item[Pre-Condition] A operational DT installation, an
			operational SAL server agent and an accessible SRB.
			\item[Post-Condition] An SRB browser is able to visualise sensor data. 
	\end{description}

\subsubsection{Metadata which comes with the sensor data is dumped into a SRB}
	There is a software implementation available which is able to receive metadata
	together with related sensor data from the Data Turbin and store it within a
	SRB using the determined format of \autoref{sec:req_dataformat}.
	
	\begin{description}
			\item[Pre-Condition] A operational DT installation, an
			operational SAL server agent and an accessible SRB.
			\item[Post-Condition] An SRB browser is able to visualise sensor data
			related with metadata.
	\end{description}

%EOF